codeSnippets/snippets/client-auth-oauth-google/src/test/kotlin/ApplicationTest.kt (1)

44-58: Consider closing the HttpClient after use.

While less critical for tests with MockEngine, closing the client is good practice to demonstrate proper resource management in sample code.

♻️ Suggested improvement

-        val client = HttpClient(engine) {
-            install(Auth) {
-                bearer {
-                    loadTokens {
-                        BearerTokens("invalid", "refresh")
-                    }
-
-                    refreshTokens {
-                        BearerTokens("valid", "refresh")
-                    }
-                }
-            }
-        }
-        val response = client.get("https://test.example")
-        assertEquals(HttpStatusCode.OK, response.status)
+        val client = HttpClient(engine) {
+            install(Auth) {
+                bearer {
+                    loadTokens {
+                        BearerTokens("invalid", "refresh")
+                    }
+
+                    refreshTokens {
+                        BearerTokens("valid", "refresh")
+                    }
+                }
+            }
+        }
+        client.use {
+            val response = it.get("https://test.example")
+            assertEquals(HttpStatusCode.OK, response.status)
+        }

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@codeSnippets/snippets/client-auth-oauth-google/src/test/kotlin/ApplicationTest.kt`
around lines 44 - 58, The HttpClient instance named client in the test is not
closed; update the test to properly dispose of it after use by invoking
client.close() or using the client's use/auto-close pattern around the request
so HttpClient resources are released; locate the HttpClient(...) block and the
subsequent client.get call and ensure the client is closed afterward (e.g., call
client.close() or wrap client creation in a use scope).

topics/client-auth.md (1)

174-176: Consider varying bullet sentence openings for smoother scanability.

All three bullets start with “When”, which reads a bit repetitive.

✍️ Suggested wording tweak

-* When the user logs out.
-* When credentials or tokens stored by your application change.
-* When you need to force providers to reload the authentication state on the next request.
+* After a user logs out.
+* If credentials or tokens stored by your application change.
+* To force providers to reload the authentication state on the next request.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@topics/client-auth.md` around lines 174 - 176, The three bullets ("When the
user logs out.", "When credentials or tokens stored by your application
change.", "When you need to force providers to reload the authentication state
on the next request.") are repetitive because they all begin with "When"; reword
them for variety and smoother scanning by changing sentence openings (e.g., "On
user logout.", "If credentials or stored tokens change.", "To force providers to
reload the auth state on the next request."). Update the three bullet lines in
topics/client-auth.md accordingly while preserving their original meaning.